Release 10.1A: OpenEdge Development:
Progress Dynamics Repository Reference

ryc_ui_event table — rycue

This table stores information about user interface (UI) events for a SmartObject. It works like the ryc_attribute_value table. UI events can be associated with object types, SmartObjects, and SmartObject instances. This allows the attachment of UI events to dynamic objects.

Table 10–23 lists the table’s FLA, fields, and foreign keys.

Table 10–23: ryc_ui_event table information 

Table FLA	Fields (data type)	Foreign keys
rycue	ui_event_obj (Decimal) object_type_obj (Decimal) container_smartobject_obj (Decimal) smartobject_obj (Decimal) object_instance_obj (Decimal) event_name (Character) constant_value (Logical) action_type (Character) action_target (Character) event_action (Character) event_parameter (Character) event_disabled (Logical) primary_smartobject_obj (Decimal) render_type_obj (Decimal)	object_instance_obj object_type_obj render_type_obj smartobject_obj

Table 10–24 gives details of the table’s indexes.

Table 10–24: ryc_ui_event index information 

Index name	Elements	Type
XPKryc_ui_event	ui_event_obj	Primary Unique
XAK1ryc_ui_event	object_type_obj smartobject_obj object_instance_obj render_type_obj event_name	Unique
XIE1ryc_ui_event	primary_smartobject_obj	Nonunique
XIE2ryc_ui_event	object_instance_obj	Nonunique
XIE3ryc_ui_event	container_smartobject_obj	Nonunique
XIE4ryc_ui_event	smartobject_obj	Nonunique
XIE5ryc_ui_event	render_type_obj	Nonunique

When creating entries in this table for events associated with an object type, the object numbers for the SmartObject and instance are 0.

When creating entries in the table for a SmartObject, the object type field is populated to avoid having 0 in the key. When creating events for an object instance, both the object type and the SmartObject are populated. This ensures effective use of the alternate keys.

Note: When you look for the attributes for an object type, check for the specific object type and 0 values for the SmartObject and instance fields.

Events are not cascaded down to subclasses. Entries only exist at subclass levels for overrides. To retrieve all events for an object, you must read the events for all the object’s parent classes.

When multiple rendering engines are supported and used, the render_type_object adds another dimension to the possible events. You can specify a rendering engine type for events at the class, master, and instance levels. If an event is specified at the class level for a specific rendering engine type and not for a 0 rendering engine type, then that event is only used for the specific rendering engine type and is not applied across all rendering engines.